Reusable dynamic object in runtime environment

ABSTRACT

An embodiment, of the disclosure provides a method for using a reusable dynamic object in a runtime environment. The method includes: (a) configuring, using an object dictionary, properties of the dynamic object; (b) setting a persistence state for the dynamic object; (c) setting a hierarchy state for the dynamic object; (d) establishing a create data buffer, a read data buffer, an update data buffer, and a delete data buffer; and (e) instantiating the dynamic object at runtime, wherein the object dictionary includes an object structure, a logical to physical mapping, a persistence configuration, and object relationships for a plurality of dynamic objects, and the create data buffer, the read data buffer, the update data buffer, and the delete data buffer execute data persistence mechanisms based on the persistence configuration of the dynamic object.

BACKGROUND

Development of modern software applications is highly complex and timeconsuming. Businesses increasingly develop and deploy larger and morecomplex applications. Additionally, these applications are oftencritical to a business's success. It is often difficult to develop theselarge complex applications on time, while meeting the project budget,and avoiding bugs and errors in the software application.

Approximately 80% of software development project time is spentdesigning, building, and testing model and controller layer objects. Themodel and controller layers connect the user presentation layer to theunderlying data store. Attempts to streamline this process via objectand relational mapping frameworks has led to highly proprietary andfragile software.

Representational state transfer (RestFUL) APIs have been developed toprovide interoperability between computer systems. However, this methodhas added yet another layer of code to the application architecture andrequire even more coding and testing.

Some applications utilize common software design patterns. However, thisresults in highly complex, fine grained applications that costsubstantially more to develop and are typically harder to understand. Inaddition to being more complex, much of this code is behind the scenesand has very little visible value to business users.

SUMMARY

An embodiment of the disclosure provides a method for using a reusabledynamic object in a runtime environment. The method includes: (a)configuring, using an object dictionary, properties of the dynamicobject; (b) setting a persistence state for the dynamic object; (c)setting a hierarchy state for the dynamic object; (d) establishing acreate data buffer, a read data buffer, an update data buffer, and adelete data buffer; and (e) instantiating the dynamic object at runtime,wherein the object dictionary includes an object structure, a logical tophysical mapping, a persistence configuration, and object relationshipsfor a plurality of dynamic objects, and the create data buffer, the readdata buffer, the update data buffer, and the delete data buffer executedata persistence mechanisms based on the persistence configuration ofthe dynamic object.

Another embodiment of the disclosure provides a server for using areusable dynamic object in a runtime environment. The server includes aprocessor and a non-transitory computer readable medium containinginstructions stored thereon, such that when the instructions areexecuted by the processor, the server performs the method including: (a)configuring, using an object dictionary, attributes of the dynamicobject; (b) setting a persistence state for the dynamic object; (c)setting a hierarchy state for the dynamic object; (d) establishing acreate data buffer, a read data buffer, an update data buffer, and adelete data buffer; and (e) instantiating the dynamic object at runtime,wherein the object dictionary includes an object structure, a logical tophysical mapping, a persistence configuration, and object relationshipsfor a plurality of dynamic objects, and the create data buffer, the readdata buffer, the update data buffer, and the delete data buffer executedata persistence mechanisms based on the persistence configuration ofthe dynamic object.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 illustrates a high level dynamic object that stores abstractclass definitions according to some embodiments;

FIG. 2 illustrates components of a computing device according to someembodiments; and

FIG. 3 illustrates a flow diagram for using a reusable dynamic object ina runtime environment.

DETAILED DESCRIPTION

Embodiments of the disclosure provide a dynamic object softwarecomponent. A dynamic object is a runtime software component thatimplements model driven development concepts. Dynamic objects streamlineapplication development time, reduce runtime resources, and provide aconceptual programming model. Dynamic objects further provide amechanism for rapidly transforming business requirements into softwarecode.

In some embodiments, a dynamic object encapsulates numerous otherobjects. For example, a dynamic object may encapsulate a data accessobject, a value object, an object factory, and facade design patternsaccording to industry standard design patterns. A data access object maybe defined as an object that provides an interface to a database oranother persistence mechanism. A value object is an immutable object. Anobject factory is an object used to create other objects. A façadedesign pattern is an object that provides a simplified interface to alarger or complex body of code. A dynamic object may inherit itsstructure from an object dictionary or another dynamic object. Further,a dynamic object can represent persistent or non-persistent businessobjects. Dynamic objects when instantiated at runtime are calledbusiness objects. Physical models and persistence mechanisms may beembedded in the dynamic object. Thus, a common set of mechanisms andfeatures may be provided regardless of the data storage orsynchronization mechanisms. For example, the dynamic object mayimplement SQL (structured query language), flat file, middleware, EJB(enterprise java bean), or other persistence mechanics vis a common setof features and mechanisms. An application developer is therefore, notresponsible for writing any of the persistence code. The underlying codeis transparent to the application developer.

Dynamic objects provide a streamlined application architecture referredto as a Dynamic Application which provides the core applicationinfrastructure for client server, web, desktop, or distributedapplications. Multiple Dynamic Applications can communicate viamiddleware providing a shared data state across the multiple DynamicApplications which results in improved state management, lessapplication overhead, and faster performance.

Dynamic objects are instantiated at runtime and all dynamic objectsutilize a single set of code. The dynamic object is a collection ofclasses that uses a single set of code for all applications, and eachapplication instantiates a single copy of the set of code to supportmultiple instances of all dynamic objects. In some embodiments,properties (or attributes) of a dynamic object are configured atinstantiation via an object dictionary. Properties of a dynamic objectmay also be instantiated via referencing an existing dynamic object.Since dynamic objects may exhibit object persistence and may beorganized in a hierarchy, the persistence and hierarchicalcharacteristics may be configured at runtime.

Dynamic objects may also support traditional inheritance, wheretraditional inheritance may be one avenue used to modify behavior of thedynamic object. Traditional inheritance refers to the ability to extendthe capabilities of a dynamic object without altering the core code thatthe dynamic object is instantiated from. A dynamic object containsexposed methods which may be used to configure parent-childrelationships between objects as well as set persistence mechanisms ofthe dynamic object.

The dynamic object is a foundation class that provides all of the dataaccess functionality. The dynamic object is also a container class thathas the following primary collections: ObjectProperties andPropertyValues. The ObjectProperties collection contains objectmetadata, and the PropertyValuesTable contains property or attributestates. Multiple attribute and property buffers contain the current,filtered, original, edited, and deleted data underlying thePropertyValues. The dynamic object can be created in multipleprogramming languages, for example, Java and Microsoft Visual Basic. Thedynamic object utilizes name/value pairs to represent theproperties/values, however the underlying mechanisms can be implementedwith a variety of collection mechanisms such as arrays, maps,collections, and so on.

FIG. 1 illustrates an example of a high level dynamic object 100 thatstores abstract class definitions according to some embodiments. Thehigh level dynamic object 100 may include a definition for a dynamicobject 102, and the dynamic object 102 may have parent-childrelationships and dependencies between various other objects. In thehigh level dynamic object 100, the dynamic object 102 is shown to be aparent to an object property interface 104, a collection of dynamicobjects (collection dynamic object 106), a data store interface 108, aselection criteria interface 110, and a collection of property valueslabeled as collection PropertyValuesTable 112, which is a tableincluding one or more property value interfaces 114. Each of the objectproperty interface 104, the collection dynamic object 106, the datastore interface 108, the selection criteria interface 110, thecollection PropertyValuesTable 112 and the property value interface 114may include properties and methods. Each of the object propertyinterface 104, the collection dynamic object 106, the data storeinterface 108, the selection criteria interface 110, and the propertyvalue interface 112 are dynamic objects. FIG. 1 shows the dynamic object102 being a parent, but other configurations may be set up where thedynamic object 102 is a child. In the embodiment of FIG. 1, one or moremethods in the dynamic object 102 is utilized to configure theparent-child relationship. The dynamic object 102 further includes oneor more properties in addition to one or more methods. Properties mayinclude variables that are defined in the dynamic object; these include,for example, an object identity, object owner, object name, an objectclass, an object description, a persistence indicator, a read onlyindicator, a database table, and so on. Methods may include one or moreGet operators for reading variables or data stored in the dynamic object102; these include, for example, GetData( ), GetProperty( ),GetObjectOwner( ), GetObjectName( ), GetObjectDescription( ), and so on.Methods may also include Set operators for defining variables within thedynamic object 102; these include, for example, SetProperty( ), NewData(), InheritAncestorProperties( ), Generateldentifier( ), and so on.Methods may further include Move operators for manipulating data withinthe dynamic object 102; these include, for example, MoveToRecord( ),MoveFirst( ), MoveNext( ), and so on.

The different Get operators may be described as follows. GetData( )fetches data from a database where the dynamic object 102 stores data.GetProperty( ) returns a value of a property. GetObjectOwner( ) returnsan owner of the dynamic object. GetObjectName( ) returns a name of thedynamic object. GetObjectDescription( ) returns a description of thedynamic object. The different Set operators may be described as follows.SetProperty( ) sets a property to a value. NewData( ) creates a newrecord in original and edit buffers. InheritAncestorProperties( )executes metadata inheritance mechanism by inheriting ObjectPropertiesmetadata from an existing instance of a dynamic object.Generateldentifier( ) is used to generate an identifier for the dynamicobject. The different Move operators may be described as follows.MoveToRecord( ) moves a record pointer to a specified record in the editbuffer. MoveFirst( ) moves a record pointer to the first record in theedit buffer. MoveNext( ) moves a record pointer to the next record inthe edit buffer.

The high level dynamic object 100 contains the object definition alongwith multiple data buffers to control the standard create, read, update,and delete style persistence mechanisms. These buffers may include anoriginal buffer, a filter buffer, an edit buffer, and a delete buffer.The original buffer may be used to hold property values at objectinstantiation. The edit buffer may be used to hold property values ofobjects with values that have changed since object instantiation. Thedelete buffer may be used to mark property values that have been removedfrom an instantiated object. Utilizing these multiple buffers, the highlevel dynamic object 100 is able to create, read, update, and deleteproperty values during runtime.

The dynamic object 102 may have methods that point to the objectproperty interface 104. The object property interface 104 may haveproperties and methods. Properties of the object property interface 104may include several variables including a property identity, a propertyname, a property description, and so on. Methods under the objectproperty interface 104 may include one or more Get operators for readingvariables or data stored in the object property interface 104.

The dynamic object 102 may have methods that point to the collectiondynamic object 106. Collection dynamic object 106 is a collection ofdynamic objects, meaning that the collection dynamic object 106 servesas a parent to one or more dynamic objects. For example, the collectiondynamic object 106 may serve as a parent to another collection dynamicobject, an object property interface, a data store interface, aselection criteria interface, and a property value interface. Thecollection dynamic object 106 may include one or more methods to manageproperties in the collection dynamic object 106 or its children. Forexample, the methods may include an AddProperty( ) or Remove( ) methodif the collection dynamic object 106 is a parent of an object property;an AddCriterion( ) or Remove( ) method if the collection dynamic object106 is a parent of a selection criterion object; and a HasChanged( ) orRemove( ) method if the collection dynamic object 106 is a parent of aproperty value object. The AddProperty( ) adds or changes a key/valuepair of a dynamic object. AddCriterion( ) adds a criterion for querypurposes. Remove( ) removes a key/value pair from a dynamic object.HasChanged( ) returns a value indicating whether any value in thecollection has changed.

The dynamic object 102 may have methods that point to the data storeinterface 108. The data store interface 108 may be a dynamic object withproperties and methods directed at a data store. Properties of a datastore interface 108 may include a type of data store, a persistence ofthe data store, a maximum number of records for the data store, and soon. Methods of the data store interface 108 may include one or more Getoperators.

The dynamic object 102 may have methods that point to the selectioncriteria interface 110. The selection criteria interface 110 may be adynamic object with properties and methods directed at identifying whichrecords to fetch from a data store while using one of the Get operators.Properties of the selection criteria interface 110 may include aproperty name, an operation, a data type, and so on. The selectioncriteria interface 110 may include one or more Get operators.

The dynamic object 102 may have methods that point to the property valueinterface 114. The property value interface 114 may be a dynamic objectwith properties and methods that allow access to internal property data.Properties of the property value interface 112 may include whether aproperty has changed, and methods of the property value interface 112may include one or more Get operators.

The high level dynamic object 100 is a collection of objects (dynamicobject 102, collection dynamic object 106, object property interface104, property values table 112, property value interface 114, data storeinterface 108, and selection criteria interface 110) that store theabstract class definitions, with each dynamic object in the classinheriting its definition from an object dictionary at instantiation.Dynamic objects can also inherit their definition from existinginstances of dynamic objects. This mechanism allows for storing a singleinstance of the data and allowing multiple objects to share the data.

The underlying storage mechanism of a dynamic object is name/value pairsalong with each property's detailed definition. Each dynamic objectcontains the object definition along with multiple data buffers tocontrol the standard Create, Read, Update, and Delete style persistencemechanisms. In an embodiment, the multiple data buffers may be definedin a single method, for example, an updateData( ) method which maydelete all records from a delete buffer; cursor through an edit buffer,and save each record in the edit buffer; reset the delete buffer; resetall edit buffer records to not changed; and copy the edit buffer to anoriginal buffer. The combination of the underlying data storage and theexposed methods greatly reduces the effort to generate RESTFul orWebService application programming interfaces (APIs) from dynamicobjects.

Since a dynamic object can inherit its properties from either an objectdictionary or from another dynamic object, an application may load asingle instance of object properties that are shared across allinstances of the object class. For example, in FIG. 1, an instance of aproperty value interface using the object dictionary 100 may refer tovalues stored in a parent dynamic object 102. In addition, a dynamicobject can either be persistent or non-persistent. Non-persistentdynamic objects automatically pipe all data requests to their ancestors.This mechanism is referred to as the data bus. Dynamic objects may beimplemented as software objects in multiple software platforms, forexample, .NET, java, and so on. Each of the host development languagesallow any dynamic object to contain a reference to another dynamicobject. This communications mechanism can be used to pass data acrossobject boundaries via dynamic object methods such as the SetProperty( )and GetProperty( ) methods.

In some embodiments, dynamic objects support event based communications.For example, evoking the SetProperty( ) method in a child object raisesan event. The event allows a parent object to intercept the SetProperty() event. This communications mechanism may be used to hook data changeevents and add business rules.

FIG. 2 illustrates components of a computing device 200 according tosome embodiments. Computing device 200 may include one or moreprocessors 202, memory 204, network interfaces 206, power source 208,output devices 210, input devices 212, and storage devices 214. Eachcomponent provided is interconnected physically, communicatively, and/oroperatively for inter-component communications in order to realizefunctionality ascribed to one or more computers or devices running adynamic application according to embodiments of the disclosure. Tosimplify the discussion, the singular form will be used for allcomponents identified in FIG. 2 when appropriate, but the use of thesingular does not limit the discussion to only one of each component.For example, multiple processors may implement functionality attributedto processor 202.

Processor 202 is configured to implement functions and/or processinstructions for execution within the computing device 200. For example,processor 202 executes instructions stored in memory 204 or instructionsstored on a storage device 214. In certain embodiments, instructionsstored on storage device 214 are transferred to memory 204 for executionat processor 202. Memory 204, which may be a non-transient,computer-readable storage medium, is configured to store informationwithin the computing device 200 during operation. In some embodiments,memory 204 includes a temporary memory that does not retain informationstored when the computing device 200 is turned off. Examples of suchtemporary memory include volatile memories such as random accessmemories (RAM), dynamic random access memories (DRAM), and static randomaccess memories (SRAM). Memory 204 also maintains program instructionsfor execution by the processor 202 and serves as a conduit for otherstorage devices (internal or external) coupled to the computing device200 to gain access to processor 202.

Storage device 214 includes one or more non-transient computer-readablestorage media. Storage device 214 is provided to store larger amounts ofinformation than memory 204, and in some instances, configured forlong-term storage of information. In some embodiments, the storagedevice 214 includes non-volatile storage elements. Non-limiting examplesof non-volatile storage elements include floppy discs, flash memories,magnetic hard discs, optical discs, solid state drives, or forms ofelectrically programmable memories (EPROM) or electrically erasable andprogrammable (EEPROM) memories.

Network interfaces 206 are used to communicate with external devicesand/or servers. The computing device 200 may include multiple networkinterfaces 206 to facilitate communication via multiple types ofnetworks. Network interfaces 206 may include network interface cards,such as Ethernet cards, optical transceivers, radio frequencytransceivers, or any other type of device that can send and receiveinformation. Non-limiting examples of network interfaces 206 includeradios compatible with several Wi-Fi standards, 3G, 4G, Long-TermEvolution (LTE), Bluetooth®, etc.

Power source 208 provides power to the computing device 200. Forexample, the device 200 may be battery powered through rechargeable ornon-rechargeable batteries utilizing nickel-cadmium or other suitablematerial. Power source 208 may include a regulator for regulating powerfrom the power grid in the case of a device plugged into a wall outlet,and in some devices, power source 208 may utilize energy scavenging ofubiquitous radio frequency (RF) signals to provide power to thecomputing device 200.

The computing device 200 may also be equipped with one or more outputdevices 210. Output device 210 is configured to provide output to a userusing tactile, audio, and/or video information. Examples of outputdevice 210 may include a display (cathode ray tube (CRT) display, liquidcrystal display (LCD) display, LCD/light emitting diode (LED) display,organic LED display, etc.), a sound card, a video graphics adapter card,speakers, magnetics, or any other type of device that may generate anoutput intelligible to a user of the computing device 200. The outputdevice 210 may display a graphical user interface of the application402.

The computing device 200 may also be equipped with one or more inputdevices 212. Input devices 212 are configured to receive input from auser or the environment where the device 200 resides. In certaininstances, input devices 212 include devices that provide interactionwith the environment through tactile, audio, and/or video feedback.These may include a presence-sensitive screen or a touch-sensitivescreen, a mouse, a keyboard, a video camera, microphone, a voiceresponsive system, or any other type of input device.

The hardware components described thus far for the computing device 200are functionally and communicatively coupled to achieve certainbehaviors. In some embodiments, these behaviors are controlled bysoftware running on an operating system of the computing device 200.

FIG. 3 illustrates a process 300 for using a reusable dynamic object ina runtime environment. The process 300 is performed by a computingdevice running an application capable of instantiating one or moredynamic objects including the reusable dynamic object. Dynamic objectsare instantiated at runtime. At step 302, the application configuresproperties of the reusable dynamic object using an object dictionary.The object dictionary includes one or more object structures, a logicalto physical mapping, a persistence configuration, and objectrelationships for a plurality of dynamic objects. In some embodiments,configuring properties includes that the reusable dynamic objectincludes default properties inherited from the object dictionary. Insome embodiments, configuring properties includes that the reusabledynamic object includes default properties inherited from a seconddynamic object. In some embodiments, a dynamic object factory class isused to configure the dynamic object by passing values for one or moreof the following properties/metadata: ObjectOwner (an owner of theobject being instantiated), ObjectName (a name of the object beinginstantiated), ObjectSubClass (a class of the object beinginstantiated), ReadOnly (a Boolean indication whether the object beinginstantiated is read only), Static (a Boolean indication whether data inthe object being instantiated is static), and Ancestor (an ancestor ofthe dynamic object being instantiated). Dynamic objects that areindicated as either Static or ReadOnly may automatically fetch data atinstantiation. Dynamic objects that are not indicated as ReadOnly mayfetch data via one or more Get methods, for example, a getData( )method.

At step 304, the computing device sets a persistence state for thereusable dynamic object. The persistence state for the reusable dynamicobject may be persistent or non-persistent. In a non-persistent state,the reusable dynamic object may pipe data requests to one or more of itsancestors. In some embodiments, the computing device sets a hierarchystate for the reusable dynamic object. The hierarchy state for thereusable dynamic object may be a parent state or a child state. In anexample, the reusable dynamic object references a second dynamic objectin the hierarchy and data is passed from the reusable dynamic object tothe second dynamic object. In some embodiments, the reference to thesecond dynamic object is set using a Set property method of the reusabledynamic object. In another embodiment, the persistence state is set atinstantiation via the ReadOnly property of the instantiation method orvia a Set method, for example, the setReadOnly( ) method of the reusabledynamic object.

At step 306, the computing device establishes buffers for engaging thedynamic object. Step 306 involves instantiating the collection ofproperty values (identified in FIG. 1 as collectionPropertyValuesTables) that are used to execute data persistencemechanisms of the dynamic object. Some buffers that may be establishedinclude a create data buffer, a read data buffer, an update data buffer,an edit buffer, and a delete data buffer. These buffers will allow theuse of various methods, such as Get and Set methods, of the reusabledynamic object.

At step 308, the computing device instantiates the reusable dynamicobject at runtime. In an example, the reusable dynamic object referencesa second dynamic object a hierarchy, and based on activity in theruntime environment, data is passed from the reusable dynamic object tothe second dynamic object. In some embodiments, the reference to thesecond dynamic object is set using a Set property method of the reusabledynamic object. In some embodiments, when the Set property method of thereusable dynamic object is invoked in the application to pass data fromthe reusable dynamic object to the second dynamic object, a parentobject to the reusable dynamic object intercepts the Set property methodevent.

The development of dynamic objects is in response to challenges thathave plagued modern software development. Dynamic objects provide thefollowing benefits to software architects, engineers, and developers:(1) A common object dictionary that includes the object structure,logical to physical mapping, persistence configuration, and objectrelationships; (2) Provides methods of capturing of metadata frommodeling tools; (3) A single set of code used for all dynamic objects;(4) Objects are configured and not coded; (5) A reduction in softwareinfrastructure code development; (6) A major decrease in runtime CPU andmemory resources required to run applications; (7) Rapid application andAPI development; and (8) Introduction of streamlined applicationarchitectures.

All references, including publications, patent applications, andpatents, cited herein are hereby incorporated by reference to the sameextent as if each reference were individually and specifically indicatedto be incorporated by reference and were set forth in its entiretyherein.

The use of the terms “a” and “an” and “the” and “at least one” andsimilar referents in the context of describing the invention (especiallyin the context of the following claims) are to be construed to coverboth the singular and the plural, unless otherwise indicated herein orclearly contradicted by context. The use of the term “at least one”followed by a list of one or more items (for example, “at least one of Aand B”) is to be construed to mean one item selected from the listeditems (A or B) or any combination of two or more of the listed items (Aand B), unless otherwise indicated herein or clearly contradicted bycontext. The terms “comprising,” “having,” “including,” and “containing”are to be construed as open-ended terms (i.e., meaning “including, butnot limited to,”) unless otherwise noted. Recitation of ranges of valuesherein are merely intended to serve as a shorthand method of referringindividually to each separate value falling within the range, unlessotherwise indicated herein, and each separate value is incorporated intothe specification as if it were individually recited herein. All methodsdescribed herein can be performed in any suitable order unless otherwiseindicated herein or otherwise clearly contradicted by context. The useof any and all examples, or exemplary language (e.g., “such as”)provided herein, is intended merely to better illuminate the inventionand does not pose a limitation on the scope of the invention unlessotherwise claimed. No language in the specification should be construedas indicating any non-claimed element as essential to the practice ofthe invention.

Preferred embodiments of this invention are described herein, includingthe best mode known to the inventors for carrying out the invention.Variations of those preferred embodiments may become apparent to thoseof ordinary skill in the art upon reading the foregoing description. Theinventors expect skilled artisans to employ such variations asappropriate, and the inventors intend for the invention to be practicedotherwise than as specifically described herein. Accordingly, thisinvention includes all modifications and equivalents of the subjectmatter recited in the claims appended hereto as permitted by applicablelaw. Moreover, any combination of the above-described elements in allpossible variations thereof is encompassed by the invention unlessotherwise indicated herein or otherwise clearly contradicted by context.

1. A method for using a reusable dynamic object in a runtimeenvironment, the method comprising: configuring, using an objectdictionary, properties of the dynamic object; setting a persistencestate for the dynamic object; setting a hierarchy state for the dynamicobject; establishing a create data buffer, a read data buffer, an updatedata buffer, and a delete data buffer; and instantiating the dynamicobject at runtime, wherein the object dictionary includes an objectstructure, a logical to physical mapping, a persistence configuration,and object relationships for a plurality of dynamic objects, and thecreate data buffer, the read data buffer, the update data buffer, andthe delete data buffer execute data persistence mechanisms based on thepersistence configuration of the dynamic object.
 2. The method accordingto claim 1, further comprising: inheriting properties for the dynamicobject from the object dictionary.
 3. The method according to claim 1,further comprising: inheriting properties for the dynamic object from asecond dynamic object.
 4. The method according to claim 1, furthercomprising: setting the persistence state to persistent.
 5. The methodaccording to claim 1, further comprising: setting the persistence stateto non-persistent; and piping data requests to an ancestor of thedynamic object.
 6. The method according to claim 1, further comprising:setting a reference to a second dynamic object; and passing data fromthe dynamic object to the second dynamic object.
 7. The method accordingto claim 6, wherein the reference to a second dynamic object is setusing a set property method.
 8. The method according to claim 6, furthercomprising: intercepting, with a parent object to the dynamic object, aset property event when passing data from the dynamic object to thesecond dynamic object.
 9. The method according to claim 1, furthercomprising: setting a Boolean indicator signifying whether the dynamicobject is read only.
 10. The method according to claim 1, wherein thedynamic object includes a collection of property values and a collectionof object properties, wherein the collection of property values containsproperty states and the collection of object properties containsmetadata of the dynamic object.
 11. A server for using a reusabledynamic object in a runtime environment, the server including aprocessor and a non-transitory computer readable medium containinginstructions stored thereon, such that when the instructions areexecuted by the processor, the server performs the method comprising:configuring, using an object dictionary, properties of the dynamicobject; setting a persistence state for the dynamic object; setting ahierarchy state for the dynamic object; establishing a create databuffer, a read data buffer, an update data buffer, and a delete databuffer; and instantiating the dynamic object at runtime, wherein theobject dictionary includes an object structure, a logical to physicalmapping, a persistence configuration, and object relationships for aplurality of dynamic objects, and the create data buffer, the read databuffer, the update data buffer, and the delete data buffer execute datapersistence mechanisms based on the persistence configuration of thedynamic object.
 12. The server according to claim 11, further performingthe method comprising: inheriting properties for the dynamic object fromthe object dictionary.
 13. The server according to claim 11, furtherperforming the method comprising: inheriting properties for the dynamicobject from a second dynamic object.
 14. The server according to claim11, further performing the method comprising: setting the persistencestate to persistent.
 15. The server according to claim 11, furtherperforming the method comprising: setting the persistence state tonon-persistent; and piping data requests to an ancestor of the dynamicobject.
 16. The server according to claim 1, further performing themethod comprising: setting a reference to a second dynamic object; andpassing data from the dynamic object to the second dynamic object. 17.The server according to claim 16, wherein the reference to a seconddynamic object is set using a set property method.
 18. The serveraccording to claim 16, further performing the method comprising:intercepting, with a parent object to the dynamic object, a set propertyevent when passing data from the dynamic object to the second dynamicobject.
 19. A non-transitory computer readable medium for using areusable dynamic object in a runtime environment, the non-transitorycomputer readable medium containing program instructions that causes acomputer to perform the method comprising: configuring, using an objectdictionary, properties of the dynamic object; setting a persistencestate for the dynamic object; setting a hierarchy state for the dynamicobject; establishing a create data buffer, a read data buffer, an updatedata buffer, and a delete data buffer; and instantiating the dynamicobject at runtime, wherein the object dictionary includes an objectstructure, a logical to physical mapping, a persistence configuration,and object relationships for a plurality of dynamic objects, and thecreate data buffer, the read data buffer, the update data buffer, andthe delete data buffer execute data persistence mechanisms based on thepersistence configuration of the dynamic object.
 20. The non-transitorycomputer readable medium according to claim 19, further containingprogram instructions that causes the computer to perform the methodcomprising: setting a reference to a second dynamic object; and passingdata from the dynamic object to the second dynamic object.